Apparatus and method for accessing a back-end service

ABSTRACT

Aspects of the subject disclosure may include, for example, exchanging messages between a back-end-as-a-service network element and a mobile core network processor to obtain a message exchange responsive to a request for providing a mobile device with access to a back-end service of a remote system without requiring a back-end client resident at the mobile device. The messages are exchanged according to protocols operating at layers below layer five of Open Systems Interconnection (OSI) seven-layer model. Responsive to the message exchange, delivery is facilitated of the back-end service of the remote system to the mobile device. Other embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.16/257,421, filed Jan. 25, 2019, which is a Continuation of U.S. patentapplication Ser. No. 15/962,084, filed Apr. 25, 2018 (now U.S. Pat. No.10,270,688), which is a Continuation of U.S. patent application Ser. No.15/434,219, filed Feb. 16, 2017 (now U.S. Pat. No. 9,985,881), which isa Continuation of U.S. patent application Ser. No. 14/499,967, filedSep. 29, 2014 (now U.S. Pat. No. 9,609,574). All sections of theaforementioned application(s) and patent(s) are incorporated herein byreference in their entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to an apparatus and method for accessinga back-end service, and more particularly to a backend-as-a-service,software defined network element.

BACKGROUND

Mobile devices which require access to enterprise backend data sourcesgenerally rely on middleware servers, such as Mobile EnterpriseApplications Platforms (MEAP) or Mobile Applications DevelopmentPlatforms (MADP) to provide this information. For example, a mobileapplication can be written to request financial transactions from anOracle Financial database residing in an enterprise datacenter. In thisexample, the mobile device application issues data requests to a MobileEnterprise Applications Platform (MEAP) or Mobile ApplicationsDevelopment Platform (MADP) middleware gateway and/or server residing inthe enterprise data center, which subsequently accesses backend datasources, e.g., databases, and forwards this data to the mobileapplication.

In other words, when an application residing on a mobile device requiresaccess to a database, e.g., an Oracle database residing in theenterprise data center, the mobile application interfaces with amiddleware server. These servers are known by various acronyms, such as,Mobile Enterprise Applications Platforms (MEAP) or Mobile ApplicationsDevelopment Platforms (MADP).

MEAP and/or MADP gateways can be resident at datacenters of theenterprise organizations and generally receive data from a mobile deviceby way of the mobile network. In an LTE environment, the MEAP/MADPgateways receive the data from an LTE gateway. The MEAP/MADP gatewayresiding in the enterprise premises accesses backend data sources, suchas Oracle databases, and forward the information requested back to theLTE gateway for delivery to the mobile device. Thus, the LTE gatewayresiding in the carrier network essentially passes data back and forthbetween the mobile device and the MEAP/MADP servers.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a communication system thatprovides a backend-as-a-service, software defined network element;

FIG. 2 depicts another illustrative embodiment of a communication systemthat provides a backend-as-a-service, software defined network element;

FIG. 3 depicts an illustrative embodiment of a method used in portionsof the system described in FIGS. 1 and 2;

FIGS. 4-5 depict illustrative embodiments of communication systems thatprovide media services and incorporating a backend-as-a-service,software defined network element;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-2, and 4-5;

FIG. 7 depicts an illustrative embodiment of a communication device ofthe communication systems of FIGS. 1-2, and 4-5; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments of software defined network element front-ending a gatewayof the core network provides mobile devices with an ability to accessback-end data sources residing in the cloud and in enterprise customerdata centers. Mobile clients accesses services provided by asoftware-defined network, mobile backend-as-a-service network elementthat subsequently interfaces with a corresponding software-definednetwork, mobile backend-as-a-service element residing in the cloud orenterprise customer data center containing backend services. Otherembodiments are described in the subject disclosure.

The carrier is disintermediated from this process—it is just passingdata back and forth from and to the mobile device. One or more aspectsof the subject disclosure include software-defined network, mobilebackend-as-a-service network element that allow mobile devices todynamically access back-end data sources (such as Oracle and SAPdatabases) residing in the cloud or enterprise customer data centerswithout mobile middleware servers. In some instances, mobile devices canaccess the back-end data sources without requiring a resident back-endclient, or even a related application. Namely, requests for back-endservices can be made through existing messaging infrastructures, such asshort message service (SMS) or Mobile Multimedia Messages (MMS)according to the techniques disclosed herein.

One embodiment of the subject disclosure includes a device including aprocessor and a memory that stores executable instructions. Theexecutable instructions, when executed by the processor, facilitateperformance of operations that include creating a first software definednetwork element in local communication with a gateway of an evolvedpacket core of a long-term evolution network. Establishment of a firstlogical network connection is facilitated between the first softwaredefined network element and a second software defined network element inlocal communication with a remotely accessible system. A requestinitiated by a mobile device serviced by the long-term evolution networkis received for access to a service of the remotely accessible system.The request is translated and forwarding to the second software definednetwork element by way of the first logical network connection. Thesecond software defined network element forwards the translated requestto the remotely accessible system.

Another embodiment of the subject disclosure includes a machine-readablestorage medium, including executable instructions that, when executed bya processor, facilitate performance of operations. The operationsincluding creating a first software defined network element in localcommunication with equipment of a core network of a mobility network.Establishment of a first logical network connection is facilitatedbetween the first software defined network element and a second softwaredefined network element in local communication with a remotelyaccessible system. A first message is received including a requestinitiated by a mobile device serviced by the mobility network for accessto a service of the remotely accessible system. A second message isforwarded including the request to the second software defined networkelement by way of the first logical network connection. The secondsoftware defined network element forwards the second message to theremotely accessible system by way of an application programminginterface.

Yet another embodiment of the subject disclosure includes a process,including creating, by a system including a processor, a number ofsoftware defined network elements at a network carrier premises.Establishment of number of logical network connection are facilitated bythe system between the number of software defined network elements and anumber of network elements in local communication with a number ofback-end servers at enterprise premises. A request initiated by a mobiledevice is received by the system for access to a service of a particularback-end server of the number of back end servers. A location isidentified of the particular back-end server of the number of back-endservers, and forwarded by the system to the network element. The messageis forwarded by way of a logical network connection of the number oflogical network connections corresponding to the location of theparticular back-end server. The network element forwards the request tothe particular back-end server of the number of back-end servers.

FIG. 1 depicts an illustrative embodiment of a communication system 100that provides a backend-as-a-service, software defined network element.The system 100 supports mobile access to remote, back-end serviceshosted by data centers 102 a, 102 b (generally 102). A mobile device 104accesses the back-end services by way of a network infrastructure. Inthe illustrative example, the network infrastructure includes a carriernetwork 106 in communication with the data centers 102 by way of aninternet protocol (IP) network 108. The mobile device 104 accesses thecarrier network 106 by way of a radio terminal, such as an enhanced NodeB (eNB) 110.

The carrier network 106 includes a core network, such as an EnhancedPacket Core (EPC) 112 of a 4G or Long-Term Evolution (LTE) network. TheEPC or core network 112 includes one or more network elements. For LTEnetworks, the core network 112 generally includes a Serving Gateway(S-GW) 114, a Mobility Management Entity (MME) 116, a Home SubscriberServer (HSS) 118 and a Packet Data Network (PDN) Gateway (P-GW) 120 asshown. The core network gateways 114, 116, 118 and 120 are incommunication with each according to pre-defined interfaces S11, S6a,S5/S8a, as shown.

The eNB 110 is in communication with the MME 116 through an S1-MMEinterface and the S-GW 114 through an S1-U interface. Generally, the MMEhandles control plane activity, whereas the S-GW handles data or userplane activity. Information packets are routed between the P-GW 120 andone or more other networks, such as the IP network 108, an ISM networkand/or GSM network (not shown).

In some embodiments, the carrier network 106 includes a Software DefinedNetwork (SDN) controller or master 122. The SDN controller 112 is incommunication with other SDN network elements, referred to as MobileBack-End as a Service (MBAS) SDN network elements 124 a, 124 b(generally 124). It is envisioned that an SDN master controller 122implemented in the carrier premises 106 manages relationships betweenthe MBAS SDN element 124 and various MBAS SDN-e elements 140 residing inenterprise customer premises 102. The MBAS SDN elements 124 allow forimplementation of a software implementation of network elements that canbe created either as a pre-defined software resource or createddynamically in response to changing network conditions. The MBAS SDNelements 124 can serve as a front end to the core network devices, suchas the LTE gateways. In some embodiments, the MBAS SDN element 124 worksin conjunction with a software client residing in mobile devices 104.The purpose of the mobile client would be to interface with the MBAS SDNelement 124 and issue requests for backend data services. In at leastsome embodiments, the MBAS SDN element 124 operates transparently toother carrier network elements as part of the LTE gateway 120. The MBASSDN element 124 can work in close linkage with a corresponding MBAS SDNnetwork element or gateway 230 residing in the enterprise network or thecloud service provider 202.

The SDN controller 122 can be a stand-alone processor, such as a server,an element of a blade processor, or a portion of an existing processor.The MBAS SDN network elements 124 can be hosted on the same processingplatform as the SDN controller 122, and/or on another processingplatform. One or more of the MBAS SDN network elements 124 and/or theSDN controller can be in communication with storage 126 and/or aknowledge engine 128. The knowledge engine can be implemented as anArtificial Intelligence (AI) engine 128. The AI engine 128 includes orotherwise has access to a memory cache 129.

The AI engine 128 supports the MBAS SDN element 124 and provides anability to learn and anticipate data requests. In some embodiments,previously processed requests can be cached and used in subsequentqueries in a predictive manner. For example, if a mobile user requestsservices, such as reports according to a particular schedule, the AIengine 128 can determine particulars related to the report and/or theschedule. The AI engine 128, in cooperation with the MBAS SDN element124 can issue a request in anticipation of a request not yet receivedfrom the mobile user. Replies or reports resulting from suchanticipatory requests can be sent, e.g., pushed to the mobile device inan unsolicited manner. Alternatively or in addition, the unsolicitedresults/reports can be stored, e.g., at the storage 126 and anotification sent to the mobile device. The notification can be anysuitable mode, including an SMS message, an MMS message with a link tothe stored results/reports, an email message, a phone call, e.g., with apre-recorded voice message, or voice message synthesize from text toinformation the user of the mobile device 104 that the results areavailable.

The data centers 102 can belong to an enterprise organization, such as abusiness or other institution. Alternatively or in addition the datacenters 102 can belong to a third party, such as a cloud serviceprovider, e.g., Google®. Each of the data centers 102 can include aserver 130 a, 130 b (generally 130), referred to as a back-end or cloudserver, and storage 132 a, 132 b (generally 132) accessible to theserver(s) 130. The server(s) 130 can host one or more services underwhat is generally understood as a service-oriented architecture, e.g.,the SAP Enterprise Service Oriented Architecture. The services can beoffered to members, e.g., employees, of a particular enterprise, toclients or customers, to vendors or suppliers, to business partners orcollaborators, and so forth. The services can be accessed inmachine-to-machine transactions from within the premises of theenterprise and/or remotely at an associated network address and by wayof network connectivity to the remote machine.

In the illustrative example, the mobile device 104 includes anapplication program or “app” 134 that may be accessed or otherwiselaunched by way of an icon 136 displayable on a user interface of themobile device 104. In this example, the mobile app 134 accesses back-endservices available from the back-end servers. In some embodiments, themobile device 104 includes a resident back-end client 138 to accessservices offered by the back-end server(s) 130. Examples of servicesinclude business applications related to one or more of accounting,distribution, production, procurement, sales, customer service,corporate performance and governance, human resource and so on.

Consider a corporate performance application 134 requiring access tofinancial reports of the corporation. The application 134 can call onthe back-end client 138 to initiate a machine-machine communicationbetween the mobile device 104 and the back-end server 130 a at theenterprise data center 102 a. The back-end client 138 can generate arequest for information and send the request to the back-end server 130a. The back-end server 130 a, responsive to receiving the request, canaccess stored financial data from the storage 132 a. In someembodiments, a middleware server can be used to translate or otherwisemodify the request to a format appropriate for the back-end server 130a. The back-end server 130 a, in turn, can produce and in at least someinstances format the requested information in a report, as may beappropriate, e.g., for the particular application 134.

In the previous example, communications between the mobile device andthe back-end server rely on a client-server model that can include amiddleware server, as may be required. Particulars of the request andthe returned information or reports can be managed by the client-serverarrangement. Namely, knowledge of particular request, formats and so onare generally identified beforehand. The back-end client 138 can preparerequests and replies according to requirements of one or more of theapplication 134, the middleware servers (when provided), and theback-end server 130 a. In such instances, the carrier network 106, andparticularly the core network 112 largely relay messages between themobile device 104 and the enterprise data center 102 a. It isconceivable that for a large, e.g., national carrier, the number ofenterprise data centers can be in the hundreds or greater. Consider atleast 500 such data centers 102, one enterprise data center 102 for eachof the Fortune 500 companies.

Beneficially, the MBAS SDN element(s) 124 are resident at the carriernetwork premises and therefore closely and reliably accessible toelements of the carrier network, such as the gateways of the corenetwork 112. Accordingly, communications between the MBAS SDN elements124 and the locally accessible gateways of the core network 112 can bereliably and securely accomplished by low level interfaces. For example,the interfaces can be accomplished by one or more of layers 1-4 of theOSI model, without requiring layers 5-7. Alternatively, or in addition,the MBAS SDN elements 124 and the locally accessible gateways of thecore network 112 can communicate over other low-level interfacesincluding proprietary interfaces that may include limited or no errordetection and/or error correction. The interfaces may include limited orno security, as such security would not be necessary considering theMBAS SDN elements 124 are under the direct control of the carrier, e.g.,located on secure carrier premises. Such low-level interfaces cansimplify protocol stacks and associated network communications.

In the illustrative embodiment, the MBAS SDN element(s) 124 can initiatea logical network path to equipment at the enterprise data center(s)102, such as the back-end server(s) 130. Such logical network paths canbe pre-configured, e.g., during provisioning. Alternatively or inaddition, the logical network paths can be added, deleted and/orreconfigured on-the-fly. Such an adaptive nature of the logical networkallows the carrier network to adjust the logical network paths as may benecessary to respond to changing network conditions. Further, by usinglogical network elements 124, the provisioning of network paths can beaccomplished without regard to the underlying physical networkconnections. This allows the carrier to adjust the network in an ad hocor reactive manner.

In some embodiments, the mobile device is not equipped with nor does itrequire the back-end client 138. Rather, the MBAS SDN element(s) 124 atthe core network 112 is configured to receive request directly from theapplication 134. These can include requests directed from theapplication 134 and/or from a user of the mobile device 104 by anysuitable means, such as text messages through SMS or text/multimediamessages through MMS. The MBAS SDN element(s) 124 can receivesupplemental information from the message itself and/or from thecarrier.

The supplemental information an include one or more of identities of themobile device 104, a user of the mobile device 104, the application 134,the enterprise data center 102, the back-end server 130, a servicerequested from the back-end server 130, and so on. The supplementalinformation can be obtained from the message, e.g., in a header portion.Alternatively or in addition, all or a portion of the supplementalinformation can be provided by the carrier. Such carrier-providedinformation can include network information, such as one or more ofstatistics, capacity, billing, as a real time value based on currentconditions. It is also envisioned that the network information caninclude historical information, e.g., past usage, and/or predictiveinformation, such as expected outages, limitations to bandwidths,changes in billing rates, and so on.

The MBAS SDN network element(s) 124 can exchange messages between itselfand the back end server(s) 130 without modification. Alternatively or inaddition, the MBAS SDN network element(s) 124 can intercept suchmessages, translate and/or reformat, as may be required. Thus, anapplication might use a particular set of commands that are notrecognizable or otherwise serviceable directly by the back-end server.

An example includes an SMS message typed by a user: “provide secondquarter financials.” This SMS message could be relayed directly to theMBAS SDN via another network entity, such as Short Message Peer-to-Peer(SMPP) gateway. The MBAS SDN 124 a might receive this message directly,e.g., by a user sending it via SMS addressed to a short code identifyingone of the SDN controller 122 and/or the MBAS SDN 124 a. It isenvisioned that the MBAS SDN element 124 is supported by a large set ofcatalogs and databases, which would contain records, such as records ofmobile clients, requests, associated databases and location of MBASSDN-e elements 140. For example, the MBAS SDN element 124 can besupported by a security catalog, which would enable the MBAS SDN element124 to restrict usage and assign privileges to individual requests basedon pre-provisioned parameters. The MBAS SDN 124 a has access to storedinformation 126 and/or the AI engine 128. The MBAS SDN 124 a can beprogrammed to directly translate message, for example, according to alook up table as might be stored in the local storage 126.Alternatively, some degree of interpretation may be necessary. Aninterpretive feature is advantageous, particularly for such free-formmessages as those provided by email, SMS, MMS and so on.

According to generally well understood techniques, such free formmessages can be parsed according to one or more of a grammar and adictionary. The parsed message in whole or in part can be interpretedand translated or otherwise used to generate another message. The othermessage is destined for the target back-end server 130 a and subscribesto grammars, semantics, and/or syntax as may be required by applicationsserviced by the back-end server 130 a. Certain words, e.g., thoserelated to a particular application, such as finance, governance, humanresources can be used to identify one or more of the particular back-endserver 130 a or back-end service of multiple services hosted by theserver 130 a to receive the message. Such partial identifications can beused to facilitate interpretation.

For example, having determined that the message relates to financialservices can reduce the set of possible messages available by afinancial back-end service. Other message content, such as date(s),amount(s), entities, formats, and so on can be interpreted. The MBAS SDN124 a and/or the SDN controller 122 can translate the message, e.g., theSMS text message, to a translate message suitable for the intended backend service. Other information, such as an identity of the mobile userand/or mobile device can be used to identify the particular enterprisedata center 102 a and/or the particular back-end server 130 a orback-end service sought.

In some embodiments, one or more of the enterprise data centers 102include a software defined network element 140 a, 140 b (generally 140).In particular the software defined network element is in communicationwith the mobile back-end server 130 a and referred to as a MobileBack-End as a Service, Software Defined Network enterprise (MBAS SDN-e)element 140. The MBAS SDN-e element 140 can be hosted on a dedicatedprocessor, such as a server or gateway at the enterprise data center102. Alternatively, the MBAS-SDN element 140 can be hosted on anexisting processor, e.g., supporting other activities at the enterprisedata center 102. It is envisioned that the MBAS-SDN element 140 caninclude one or more Application Programming Interfaces (APIs) 142 a, 142b (generally 142) as may be necessary to support interaction with thoseback-end services made available to the mobile user. The MBAS SDN-eelements 140 can receive requests from the carrier MBAS SDN element 124and interface via API's 142 with the backend data sources 130 such asOracle databases. An MBAS SDN-e element 140 residing in the enterprisenetwork or cloud services provider 102 can be implemented as astandalone gateway or as part of a router or additional gateways. It isalso envisioned that the MBAS SDN-e element 140 residing in theenterprise network 102 can be implemented as part of a MADP/MEAP gatewayas software defined network element. When present, the MBAS-SDN-eelement 140 at the enterprise data center 102 communicates with the MBASSDN element 124 at the core network 112 by way of the logical networkconnection established between the two devices 140, 124.

FIG. 2 another illustrative embodiment of a communication system 200that provides a backend-as-a-service, software defined network element.The system 200 supports mobile access to remote, back-end serviceshosted by one or more data centers 202. A first mobile device 204 aaccesses the back-end services by way of a network infrastructure. Inthe illustrative example, the network infrastructure includes a carriernetwork 206 in communication with the data center 202 by way of aninternet protocol (IP) network 208. The first mobile device 204 aaccesses the carrier network 206 by way of a radio terminal, such as anenhanced Node B (eNB) 210.

The carrier network 206 includes a core network 212, e.g., of an LTEnetwork. The core network 212 includes one or more network elements,such as an S-GW 214, an MME 216, an HSS 218 and a P-GW 220 as shown. TheeNB 210 is in communication with the MME 116, which generally handlescontrol plane activity and the S-GW 224 in further communication withthe P-GW 220, which generally handle user or data plan activity.Information packets are routed between the P-GW 220 and one or moreother networks, such as the IP network 208, an IMS network 254 and/orGSM network 252. In the illustrative example, a second mobile device 204b communicates with the GSM network 252 by way of a base transceiverstation 250. One or more of the GSM network 252 and the IMS network 254can be in communication with the carrier network 206 by a directconnection, e.g., by way of the P-GW 220, or indirectly, by way ofanother network, such as the IP network 208.

Also shown are an SMS gateway 256 and an MMS gateway 258 for passing SMSand/or MMS network messages according to generally well understoodtechniques. Since the MBAS SDN element 224 resides in the carriernetwork 206, it is envisioned that the MBAS SDN element 224 caninterface with other carrier network elements such as the SMS gateway256 and MMS gateway 258. The MBAS SDN element 224 can have the abilityto integrate mobile device requests with other sources of data such asthe SMS and MMS gateways 256, 258. One of the SMS gateway 256, the MMSgateway or both can be in communication with the carrier network 206,and particularly with an MBAS SDN element 225 operated by the carriernetwork 206. Such network paths between the MBAS SDN element 225 and themobile devices 204 a, 204 b (generally 204) allows SMS and/or MMSmessage to be directed from the mobile device(s) 204 directly to theMBAS SDN element 224. Once again, this can be accomplished by adestination address, such as a short code, a telephone number, or aninternet address.

The SMS and/or MMS messages, once received by the MBAS SDN element 224can be processed as described above. That is, the messages can betranslated, as required, with the translated message being directed fromthe MBAS SDN element 224 to a back-end server 230 by way of a middlewareserver, or without such a middleware server. The ability to service datarequests issued by mobile devices 204 without the need of a middlewaregateway and/or without the need of a mobile client. In some embodiments,the enterprise data center includes an MBAS SDN-e element 240 in networkcommunication with the MBAS SDN element 224 of the carrier by way of alogically defined network. The logically defined nature, along withapplication of generally well-understood software defined networktechniques allows all of the advantages and flexibility disclosed abovein reference to FIG. 1.

Messages received from the mobile device(s) 204 at the MBAS SDN 224result in one or more reply message(s) directed from the back-endserver, e.g., by way of the MBAS SDN-e element 240, to the MBAS SDN 224by way of the logical network. The MBAS SDN 224 can forward the replymessage(s) to the corresponding mobile device(s) 204. In someembodiments, messages sent by the mobile device 204 by way of SMS and/orMMS messaging services generate reply messages in a like manner Namely,an SMS request message can result in an SMS reply message. Likewise, anMMS request can result in an MMS reply. However, in some instances, asimple request message can result in a requested service that requiresfeatures not available to the source messaging service.

Consider an SMS message request for a financial report. The requestmight be a simple text phrase, e.g., “get 2013 financial report.” Theresult however, might be inappropriate for SMS for any of variousreasons. The result may be lengthy and exceed message lengths. Theresults might contain special formatting and/or graphics that are notwell suited to the messaging service used in the request. In suchinstances, one of the MBAS SDN-e element 242, the MBAS SDN 224 element224, the SDN controller 222 or another processor, such as the AI engine128 (FIG. 1) can compare the requesting message service or format andidentify a suitable reply service or format. In the simple SMS requestresulting in a length, complex result with special formatting andgraphics, the MBAS SDN-e element 242, the MBAS SDN 224 element 224, theSDN controller 222 or another processor can determine that am MMS replywould be sufficient. That is, a relatively short message indicating thata reply is present, along with a pointer, such as an HTTP or web addressto the resulting report. The web report can be sent from the back-endserver 230 to a web server, e.g., in a DMZ 260 of the enterprise datacenter or some other location, such as an Internet and/or cloud serviceprovider. Selection of the link provided in the SMS reply message willdirect the mobile device 204 to the appropriate HTTP document or webpage to view results.

Alternatively or in addition, results can be provided by other modes,such as by an email. The email address of the recipient, e.g., a user ofthe mobile device 204, can be provided according to records of theenterprise organization, the carrier, or within the message itself,e.g., during a translation. If it is recognized during a translationthat the originating message format or service would be insufficient orotherwise inadequate for a reply, the MBAS SDN 224 can include suchinformation within the translated message. That is, the translatedmessage might simply identify a mode for providing the requested serviceaccording to a user preference, an enterprise preference, bestpractices, and so on. In this instance, the MBAS SDN-e element 240receives the translated reply and notification as to which mode shouldbe used in providing the requested service.

FIG. 3 depicts an illustrative embodiment of a process 300 used inportions of the system described in FIGS. 1-2 and 4-5. Asoftware-defined network element is created at a carrier networkfacility at 302. For example, the MBAS SDN element 124 a can be createdon a processor at carrier network premises housing the core network 112.A logical network connection between the software-defined networkelement at the carrier network facility and a network entity in localcommunication with a remotely accessible system at 304. The logicalnetwork connection can be established between the MBAS SDN 124 a at thecarrier network premises and the MBAS SDN-e element 140 a at theenterprise organization premises, such as the enterprise data center 102a. The logical network can be established using generally wellunderstood techniques related to software defined networks. In otherembodiments, the logical network can be established between the MBAS SDNelement 124 a and a middle ware server, a dedicated network element,such as a router, a switch or a gateway in network communications withthe back-end server 130 a.

A request is received at the software-defined network element of thecarrier network facility at 306. For example, a request from the mobiledevice 104 in the form of a request message is directed to a networkaddress of the MBAS SDN element 124 a. By its close association andcolocation with the core network 112, the message received by way of thecore network 112 can be directed to the MBAS SDN element 124 a by way ofa low-level interface. That is, a low-level interface of one of the corenetwork gateways, such as the P-GW 120. The low-level interface alone orin combination with a close network association provided by the networkcommunications established between the MBAS-SDN element 124 a and theMBAS SDN-e element 140 a generally result in efficient, reliable andsecure delivery of back-end enterprise services to mobile users.

In some embodiments, a determination is made at 308, whether thereceived request requires translation at 308. In some instances, themobile application 134 provides the request message in a suitableformat, e.g., with proper grammar, syntax and so forth. For example,translations may not be required if the mobile device 104 includes aback-end client 138 that is pre-configured to issue request for back-endservices in a suitable formats. In such instances, a translation wouldnot generally be required. In other instances, e.g., when the mobiledevice is not configured with the back-end client 128, at least somedegree of translation may be required. One of the SDN controller 122,the MBAS SDN 124 a or both can be configured to determine whether atranslation is required. Such determinations can be made according toone of a message header, a message syntax, a message grammar or lackthereof, and so forth. To the extent that translation is required, thetranslation is performed at 310.

Whether the request is translated or not, a determination is made nextas to whether the message requires interpretation at 312. One of the SDNcontroller 122, the MBAS SDN 124 a or both can be configured todetermine whether an interpretation is required. Such determinations canbe made according to one of a message header, a message syntax, amessage grammar or lack thereof, and so forth. To the extent that themessage does not require interpretation, the message is forwarded to theenterprise network element at 314.

To the extent the message requires interpretation, interpretation isperformed at 316. Interpretations can be performed by one or more of theMBAS SDN element 124 a, the SDN controller 122, the AI engine 128 or acombination thereof. Interpretations can be used to facilitateestablishing one of a target enterprise, a target back-end service, arecipient address, an identity of the mobile device 104 and/or the userof the mobile device 104. Alternatively or in addition, interpretationscan be used to identify details associated with a requested service,such as a time periods, associated parties, requested report(s), formatsof such reports, and so on. A modified request is generated based on theinterpretation at 318, and the modified request is forwarded to theenterprise network element at 320.

FIG. 4 depicts an illustrative embodiment of a first communicationsystem 400 for delivering media content. The communication system 400can represent an Internet Protocol Television (IPTV) media system.Communication system 400 can be overlaid or operably coupled with thecommunication systems 100, 200 of FIGS. 1 and/or 2 as anotherrepresentative embodiment of communication system 400. For instance, oneor more devices illustrated in the communication system 400 of FIG. 4can create a software defined network element in local communicationwith a gateway of a service-provider network. Establishment of a firstlogical network connection can be facilitated between the first softwaredefined network element and another network element in localcommunication with a remotely accessible back-end system. A request froma communication device for access to a service of the remotelyaccessible system is received and forwarded to the other network elementby way of the first logical network connection. The other networkelement forwards the translated request to the back-end system.

The IPTV media system can include a super head-end office (SHO) 410 withat least one super headend office server (SHS) 411 which receives mediacontent from satellite and/or terrestrial communication systems. In thepresent context, media content can represent, for example, audiocontent, moving image content such as 2D or 3D videos, video games,virtual reality content, still image content, and combinations thereof.The SHS server 411 can forward packets associated with the media contentto one or more video head-end servers (VHS) 414 via a network of videohead-end offices (VHO) 412 according to a multicast communicationprotocol.

The VHS 414 can distribute multimedia broadcast content via an accessnetwork 418 to commercial and/or residential buildings 402 housing agateway 404 (such as a residential or commercial gateway). The accessnetwork 418 can represent a group of digital subscriber line accessmultiplexers (DSLAMs) located in a central office or a service areainterface that provide broadband services over fiber optical links orcopper twisted pairs 419 to buildings 402. The gateway 404 can usecommunication technology to distribute broadcast signals to mediaprocessors 406 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 408 such as computers or televisionsets managed in some instances by a media controller 407 (such as aninfrared or RF remote controller).

The gateway 404, the media processors 406, and media devices 408 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, ZigBee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 406 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 429 can be used in the mediasystem of FIG. 4. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 400. In thisembodiment, signals transmitted by a satellite 415 that include mediacontent can be received by a satellite dish receiver 431 coupled to thebuilding 402. Modulated signals received by the satellite dish receiver431 can be transferred to the media processors 406 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 408. The media processors 406 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 432 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 433 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system400. In this embodiment, the cable TV system 433 can also provideInternet, telephony, and interactive media services.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 430, a portion of which can operate as aweb server for providing web portal services over the ISP network 432 towireline media devices 408 or wireless communication devices 416.

Communication system 400 can also provide for all or a portion of thecomputing devices 430 to function as a software-defined network server(herein referred to as SDN server 430). The SDN server 430 can usecomputing and communication technology to perform function 462, whichcan include among other things, techniques described by method 300 ofFIG. 3. That is, the SDN server 430 can host the MBAS SDN 124, 224 ofthe carrier network. For instance, function 462 of server 430 can besimilar to the functions described for one or more of the MBAS SDNelement 124, 224 or the SDN controller 122, 222 of FIGS. 1 and 2 inaccordance with method 300. The media processors 406 and wirelesscommunication devices 416 can be provisioned with software functions 464and 466, respectively, to utilize the services of software-definednetwork server 430. For instance, functions 464 and 466 of mediaprocessors 406 and wireless communication devices 416 can be similar tothe functions described for the communication devices 104, 204 of FIGS.1 and 2 in accordance with method 300.

In some embodiments, the SDN server 430 can host the MBAS SDN-e element140, 240 of the enterprise data center 102, 202. In such instances,establishment of a logical network connection can be facilitated betweenthe MBAS SDN element 424 (shown in phantom) of the mobility network 417servicing mobile devices 416.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 417 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 5 depicts an illustrative embodiment of a communication system 500employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 500 can be overlaid or operably coupledwith systems 100, 200 of FIGS. 1 and/or 2 and communication system 400as another representative embodiment of communication system 400. Asoftware defined network element can be generated in local communicationwith a gateway of a carrier network. Establishment of first logicalnetwork connection can be facilitated between the first software definednetwork element and another network element in local communication witha remotely accessible back-end system. A request from a communicationdevice for access to a service of the remotely accessible system isreceived and forwarded to the other network element by way of the firstlogical network connection. The other network element forwards thetranslated request to the back-end system.

Communication system 500 can comprise a Home Subscriber Server (HSS)540, a tElephone NUmber Mapping (ENUM) server 530, and other networkelements of an IMS network 550. The IMS network 550 can establishcommunications between IMS-compliant communication devices (CDs) 501,502, Public Switched Telephone Network (PSTN) CDs 503, 505, andcombinations thereof by way of a Media Gateway Control Function (MGCF)520 coupled to a PSTN network 560. The MGCF 520 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 520.

IMS CDs 501, 502 can register with the IMS network 550 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 540. To initiate acommunication session between CDs, an originating IMS CD 501 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 504 which communicates with a corresponding originating S-CSCF506. The originating S-CSCF 506 can submit the SIP INVITE message to oneor more application servers (ASs) 517 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 517 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 506 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 506 can submit queries to the ENUMsystem 530 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 507 to submit a query to the HSS 540 toidentify a terminating S-CSCF 514 associated with a terminating IMS CDsuch as reference 502. Once identified, the I-CSCF 507 can submit theSIP INVITE message to the terminating S-CSCF 514. The terminating S-CSCF514 can then identify a terminating P-CSCF 516 associated with theterminating CD 502. The P-CSCF 516 may then signal the CD 502 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 5 may be interchangeable. It is further noted that communicationsystem 500 can be adapted to support video conferencing. In addition,communication system 500 can be adapted to provide the IMS CDs 501, 502with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PSTN CD such as CD503 or CD 505 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 530 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 506 to forward the call to the MGCF 520 via a Breakout GatewayControl Function (BGCF) 519. The MGCF 520 can then initiate the call tothe terminating PSTN CD over the PSTN network 560 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 5 can operate as wirelineor wireless devices. For example, the CDs of FIG. 5 can becommunicatively coupled to a cellular base station 521, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 550 of FIG. 5. The cellular accessbase station 521 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 5.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 521 may communicate directly with the IMS network 550 as shownby the arrow connecting the cellular base station 521 and the P-CSCF516.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

The software-defined network server 430 of FIG. 4 can be operablycoupled to communication system 500 for purposes similar to thosedescribed above. The software-defined network server 430 can performfunction 462 and thereby provide access to back-end services to the CDs501, 502, 503 and 505 of FIG. 5 similar to the functions described forSDN controller 124, 224 of FIGS. 1 and/or 2 in accordance with method300 of FIG. 3. CDs 501, 502, 503 and 505, which can be adapted withsoftware to perform function 572 to utilize the services of thesoftware-defined network server 430 similar to the functions describedfor the mobile device 104, 204 of FIGS. 1 and/or 2 in accordance withmethod 300 of FIG. 3. The software-defined network server 430 can be anintegral part of the application server(s) 517 performing function 574,which can be substantially similar to function 462 and adapted to theoperations of the IMS network 550.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with the systems 100, 200 of FIGS. 1 and/or 2,communication system 400, and/or communication system 500 as anotherrepresentative embodiment of systems 100, 200 of FIGS. 1 and/or 2,communication system 400, and/or communication system 500. The webportal 602 can be used for managing services of systems 100, 200 ofFIGS. 1 and/or 2 and communication systems 400-500. A web page of theweb portal 602 can be accessed by a Uniform Resource Locator (URL) withan Internet browser using an Internet-capable communication device suchas those described in FIGS. 1 and/or 2 and FIGS. 4-5. The web portal 602can be configured, for example, to access a media processor 406 andservices managed thereby such as a Digital Video Recorder (DVR), a Videoon Demand (VoD) catalog, an Electronic Programming Guide (EPG), or apersonal catalog (such as personal videos, pictures, audio recordings,etc.) stored at the media processor 406. The web portal 602 can also beused for provisioning IMS services described earlier, provisioningInternet services, provisioning cellular phone services, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 462-466, and 572-574 to adapt these applicationsas may be desired by subscribers and/or service providers of systems100, 200 of FIGS. 1 and/or 2, and communication systems 400-500. Forinstance, users of the services provided by the software-defined networkcontroller 122 or software-defined network server 430 can log into theiron-line accounts and provision the servers 122 or server 430. The userscan provide information, such as personal identity information,equipment identification, security information, target back-endservices, anticipated requested services, such as particular reports,formats, data sources, and so on. Service providers can log onto anadministrator account to provision, monitor and/or maintain the systems100, 200 of FIGS. 1 and/or 2 or the software-defined network server 430.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and/or 2, andFIGS. 4-5. Communication device 700 in whole or in part can representany of the communication devices described in FIGS. 1-2 and 4-5, and canbe configured to perform portions of method 300 of FIG. 3.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofdevices of FIGS. 1 and/or 2, the media processor 406, the media devices408, or the portable communication devices 416 of FIG. 4, as well as theIMS CDs 501-502 and PSTN CDs 503-505 of FIG. 5. It will be appreciatedthat the communication device 700 can also represent other devices thatcan operate in systems of FIGS. 1 and/or 2, communication systems400-500 of FIGS. 4-5 such as a gaming console and a media player.

The communication device 700 shown in FIG. 7 or portions thereof canserve as a representation of one or more of the devices of system ofFIGS. 1 and/or 2, communication system 400, and communication system500. In addition, the controller 706 can be adapted in variousembodiments to perform the functions 462-466 and 572-574, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, the software defined networkelements disclosed herein can be applied to stationary communicationdevices, such as desktop computers, media processors, circuit-switchedcommunication devices, and so forth. Still other applications includethe SDN controller 122, 222 coordinating or otherwise managing messagetraffic between a multitude of MBAS SDN elements 124, 224 and amultitude of cloud service providers or enterprise data centers. Otherembodiments can be used in the subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the software-defined network server 430, themedia processor 406, the back-end servers 130, 230, 124, 224, the AIprocessor 128, the communication devices 104, 204, any of the corenetwork devices, such as the MME 116, 216, the HSS 118, 218, the S-GW114, 214, and the P-GW 120, 220 and other devices of FIGS. 1-2 and 4-8.In some embodiments, the machine may be connected (e.g., using a network826) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

It is appreciated that implementation of the techniques disclosedherein, such as the MBAS SDN elements 124, 224, 140, 240 allow thenetwork carrier to implement services that are generally not currentlyavailable. Such services are likely to disrupt the mobile applicationmarket with respect to how back-end services are implemented. It is alsoenvisioned that a carrier offering the types of features disclosedherein can generate a revenue stream. Revenue can be obtained frommerely hosting the MBAS SDN elements 124, 224, to message processing,storage, automatic reporting, personalization features, and so on. Suchrevenue could be obtained from cloud service providers, enterprisecustomers and/or end users.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. It is furthernoted that a computing device such as a processor, a controller, a statemachine or other suitable device for executing instructions to performoperations or methods may perform such operations directly or indirectlyby way of one or more intermediate devices directed by the computingdevice.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, and HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, ZigBee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 800.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A device comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, the operations comprising: processing an exchange ofmessages between a back-end-as-a-service network element and a networkprocessor of a packet core to obtain a processed message exchangeresponsive to a request for providing a mobile device with access to aback-end service of a remote system without requiring a back-end clientresident at the mobile device, wherein the messages are exchangedaccording to protocols operating at layers below layer five of OpenSystems Interconnection (OSI) seven-layer model; and responsive to theprocessed message exchange, facilitating delivery of the back-endservice of the remote system to the mobile device.
 2. The device ofclaim 1, wherein the processed message exchange comprises a text messageexchanged by way of a short message service, and wherein the operationsfurther comprise: interpreting the text message to generate aninterpretation of the text message; identifying the remote system basedon one of an identity of the mobile device, the interpretation of thetext message or both; and identifying a particular network element. 3.The device of claim 2, wherein the operations further comprise: whereinthe processing of the exchange of messages further comprises generatinga reply responsive to receipt of the request by the remote system; andforwarding the reply to a gateway of the packet core for delivery to themobile device by way of a mobile network.
 4. The device of claim 3,wherein the reply is directed to the particular network element, andwherein forwarding of the reply further comprises forwarding the replyby way of the short message service, wherein the request initiated bythe mobile device is serviced by an application of the remote systemwithout requiring a middleware server.
 5. The device of claim 4, whereinthe request is received from the gateway of the packet core by way of alow-level interface of the gateway without layers five through seven ofa seven-layer open systems interconnection model, and wherein theapplication comprises a business application based on one of accounting,distribution, production, procurement, sales, customer service,corporate performance, governance, human resources, of any combinationthereof.
 6. The device of claim 4, wherein the particular networkelement comprises a software defined network element, and wherein theoperations further comprise determining from network performanceinformation of a network carrier, a change in network conditions,wherein the software defined network element is created dynamically inresponse to the determining of the change in network conditions.
 7. Thedevice of claim 4, wherein the operations further comprise enforcing asecurity protocol between the particular network element and anothernetwork element.
 8. A non-transitory, machine-readable storage medium,comprising executable instructions that, when executed by a processingsystem including a processor, facilitate performance of operations, theoperations comprising: exchanging messages between a back-end networkelement and a core network processor of a mobility network to obtain amessage exchange responsive to a request for providing a mobile devicewith access to a back-end service of a remote system without requiring aback-end client resident at the mobile device, wherein the messages areexchanged according to low-level network protocols; and responsive tothe message exchange, facilitating delivery of the back-end service ofthe remote system to the mobile device.
 9. The non-transitory,machine-readable storage medium of claim 8, wherein a first message ofthe message exchange originates from a client application hosted on themobile device, and wherein the operations further comprise: interpretingthe first message to generate an interpretation of the first message;identifying the remote system based on one of an identity of the mobiledevice, the interpretation of the first message or both; and identifyinga particular network element based on the remote system.
 10. Thenon-transitory, machine-readable storage medium of claim 9, wherein thefirst message is received from a gateway of the core network processorof the mobility network by way of a low-level interface of the gateway,and wherein the client application comprises a business applicationbased on one of accounting, distribution, production, procurement,sales, customer service, corporate performance, governance, humanresources, of any combination thereof.
 11. The non-transitory,machine-readable storage medium of claim 9, wherein the message exchangecomprises a reply from the remote system, wherein the reply is generatedresponsive to a receipt of the first message by the remote system; andforwarding the reply to equipment of the mobility network to deliver thereply to the mobile device.
 12. The non-transitory, machine-readablestorage medium of claim 11, wherein the reply is directed to theparticular network element, wherein forwarding of the reply furthercomprises forwarding the reply by way of the client application, andwherein the low-level network protocols comprise protocol layers belowlayer five of Open Systems Interconnection (OSI) seven-layer model. 13.The non-transitory, machine-readable storage medium of claim 9, whereinthe operations further comprise creating the particular network elementduring a provisioning of network service.
 14. The non-transitory,machine-readable storage medium of claim 9, wherein the operationsfurther comprise enforcing a security protocol between the particularnetwork element and another network element.
 15. A method, comprising:exchanging, by a processing system including a processor, messagesbetween a back-end-as-a-service network element and a mobile corenetwork processor to obtain a message exchange responsive to a requestfor providing a mobile device with access to a back-end service of aremote system without requiring a back-end client resident at the mobiledevice, wherein the messages are exchanged according to protocolsoperating at layers below layer five of Open Systems Interconnection(OSI) seven-layer model; and responsive to the message exchange,facilitating delivery, by the processing system, of the back-end serviceof the remote system to the mobile device.
 16. The method of claim 15,wherein the exchanging of the messages further comprises exchanging, bythe processing system, a text message exchanged by way of a shortmessage service, and the method further comprising: interpreting, by theprocessing system, the text message to generate an interpretation of thetext message; identifying, by the processing system, a location of aparticular back-end server based on one of an identity of the mobiledevice, an identity of a user of the mobile device, the interpretationof the text message or a combination thereof; and identifying, by theprocessing system, the back-end-as-a-service network element based onthe location of the particular back-end server.
 17. The method of claim16, wherein the message exchange comprises a reply from the particularback-end server, wherein the reply is generated responsive to receipt ofthe request by the particular back-end server; and the method furthercomprising: forwarding, by the processing system, the reply to equipmentat premises of a network carrier to deliver the reply to the mobiledevice.
 18. The method of claim 17, wherein the reply is directed to aparticular network element, and wherein forwarding of the reply furthercomprises forwarding the reply by way of the short message service,wherein the request initiated by the mobile device is serviced by theparticular back-end server without requiring a middleware server. 19.The method of claim 18, wherein the particular network element comprisesa software defined network element, the method further comprising:determining, by the processing system, a change in network conditions;and creating, by the processing system, the software defined networkelement being created dynamically in response to the determining of thechange in network conditions.
 20. The method of claim 15, wherein theexchanging of the messages further comprises receiving the request froma gateway of a premises of a network carrier by way of a low-levelinterface of the gateway.